Auto-scroll on in-context modules

ABSTRACT

Systems and methods are disclosed which may provide modules that may be displayed in the context of a website that allow for autoscrolling between the modules upon entering required information in the modules or completing actions required by the modules. The modules may be modules for paying for items via PayPal and may include modules for entering payment information, billing information, a shipping address, creating an account, and accepting terms and conditions. The modules may be displayed within the context of the webpage when selecting a pay with PayPal link without navigating away from the webpage. As a user enters information into a module, the module will automatically scroll to the next module if the module permits automatic scrolling.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/481,586, filed on Sep. 9, 2014, the entire disclosure of which isincorporated herein by reference, and which claims the benefit of U.S.Provisional Application No. 61/875,369, filed Sep. 9, 2013, the entiredisclosure of which is incorporated herein by reference.

BACKGROUND Technical Field

Embodiments disclosed herein are related to systems and methods forauto-scrolling through interactive modules displayed in the context of awebpage.

Related Art

Typically, when a user is browsing a website and clicks a link on thewebsite to take an action or request a service provided by the link, theclick will open a new browsing window or tab, and the focus will be awayfrom the previous webpage. When the requested action or service isrelated to the content of the previous webpage, this can be a nuisanceto the user.

Moreover, if the requested action or service provided by the newbrowsing window includes form fields to be filled, the user may have tomanually scroll through each of the series of fields until completed,which can also be a nuisance for users. Moreover, this can beproblematic when the user is browsing using a mobile device.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram of a networked system, consistent with someembodiments.

FIG. 2 is a diagram illustrating a computing system, consistent withsome embodiments.

FIG. 3 is a flowchart illustrating a process for automatically scrollingthrough one or more displayed modules, consistent with some embodiments.

FIGS. 4A-4E illustrate examples of displaying and scrolling betweenmodules, consistent with some embodiments.

FIG. 5 illustrates examples of active and not active modules andacceptable ways for interacting with these modules on both desktop andmobile.

FIG. 6 provides an example of a “Pay with module” with specific rulesand functionalities for this module.

FIG. 7 provides an example of a “Billing address module” with specificrules and functionalities for this module.

FIG. 8 provides an example of a “Shipping module” with specific rulesand functionalities for this module.

FIG. 9 provides an example of an “Account creation module” with specificrules and functionalities for this module.

FIG. 10 provides an example of a “Terms and conditions module” withspecific rules and functionalities for this module.

FIG. 11 provides an example of autoscrolling and autofilling using the“Pay with module” described in FIG. 6, and the “Shipping module”described in FIG. 8.

In the drawings, elements having the same designation have the same orsimilar functions.

DETAILED DESCRIPTION

In the following description specific details are set forth describingcertain embodiments. It will be apparent, however, to one skilled in theart that the disclosed embodiments may be practiced without some or allof these specific details. The specific embodiments presented are meantto be illustrative, but not limiting. One skilled in the art may realizeother material that, although not specifically described herein, iswithin the scope and spirit of this disclosure.

There is a need for displaying content in the context of a webpagewithout navigating away from the webpage and being able to auto scrollthrough form fields of the webpage. Embodiments consistent with thisdisclosure may provide various modules which may be displayed within thecontext of the webpage without navigating away from the webpage whileproviding rules for autoscrolling from an active module to a nextmodule.

In an embodiment, a system or a method is provided to display a moduleover a current content on a display in response to activation of a linkprovided in the current content. The module may include one or morefillable forms configured to receive input from a user. The system maydetermine whether the one or more fillable forms are completed correctlyand may permit the user to navigate to a subsequent module when the oneor more fillable forms of the module are completed correctly.

In an embodiment, the user is navigated to the subsequent module byautomatic scrolling from the module to the subsequent module when theone or more fillable forms of the module are completed correctly. Inanother embodiment, the user is navigated to the subsequent module whena down button displayed on the display device is selected and the one ormore fillable forms of the module are completed correctly. The one ormore fillable forms are completed correctly when a number and a type ofcharacters or numbers are correctly filled in each fillable form of themodule. The current content remains under the module and the subsequentmodule as the modules and the subsequent module scroll over the currentcontent.

FIG. 1 is a block diagram of a networked system 100, consistent withsome embodiments. System 100 includes a client computing device 102 anda remote server 104 in communication over a network 106. Remote server104 may be a hosting server that hosts webpages and other online contentaccessible by user 108 using client computing device 102 over network106. In some embodiments, remote server 104 may correspond to a paymentservice processing server that may be maintained by a payment serviceprovider, such as PayPal, Inc. of San Jose, Calif. Remote server 104 maybe maintained by other service providers in different embodiments. Insome embodiments, remote server 104 may correspond to a payment serviceprocessing server and also host merchant-specific content. Moreover,remote server 104 may correspond to one or more servers in someembodiments.

Network 106, in one embodiment, may be implemented as a single networkor a combination of multiple networks. For example, in variousembodiments, network 106 may include the Internet and/or one or moreintranets, landline networks, wireless networks, and/or otherappropriate types of communication networks. In another example, thenetwork may comprise a wireless telecommunications network (e.g.,cellular phone network) adapted to communicate with other communicationnetworks, such as the Internet.

Client computing device 102, in one embodiment, may be implemented usingany appropriate combination of hardware and/or software configured forwired and/or wireless communication over network 106. For example,client computing device 102 may be implemented as a wireless telephone(e.g., smart phone), tablet, personal digital assistant (PDA), notebookcomputer, personal computer, a connected set-top box (STB) such asprovided by cable or satellite content providers, or a video game systemconsole, a head-mounted display (HMD) or other wearable computingdevice, including a wearable computing device having an eyeglassprojection screen, and/or various other generally known types ofcomputing devices.

Client computing device 102 may include any appropriate combination ofhardware and/or software having one or more processors and capable ofreading instructions stored on a tangible non-transitorymachine-readable medium for execution by the one or more processors.Consistent with some embodiments, client computing device 102 includes amachine-readable medium, such as a memory (not shown) that includesinstructions for execution by one or more processors (not shown) forcausing client computing device 102 to perform specific tasks. In someembodiments, the instructions may be executed by the one or moreprocessors in response to interaction by a user 108. For example, suchinstructions may include a browser application 110 such as a mobilebrowser application, which may be used to provide a user interface topermit user 108 to browse information available over network 106,including information hosted by remote server 104. For example, browserapplication 110 may be implemented as a web browser to view informationavailable over network 106. Browser application 110 may include agraphical user interface (GUI) that is configured to allow user 108 tointerface and communicate with remote server 104 or other serversmanaged by content providers or merchants via network 106. For example,user 108 may be able to access websites to find and purchase items, aswell as access user account information or web content.

Client computing device 102 may also include a payment application 112.In some embodiments, payment application 112 may be capable of providinguser 108 with an interface for making payments using client computingdevice 102 over network 106, including payments to be processed byremote server 104. Client computing device 102 may further include otherapplications 114 as may be desired in one or more embodiments to provideadditional features available to user 108, including accessing a useraccount with remote server 104. For example, applications 114 mayinclude interfaces and communication protocols that allow the user toreceive and transmit information through network 106 and to remoteserver 104 and other online sites. Applications 114 may also includesecurity applications for implementing client-side security features,programmatic client applications for interfacing with appropriate APIsover network 106 or various other types of generally known programsand/or applications.

Remote server 104 may also be maintained by an online payment provider,such as PayPal, Inc. of San Jose, Calif., which may provide processingfor online financial and information transactions on behalf of user 108.Remote server 104 may include a module application 116 which may becapable of providing one or more modules to be displayed in the contextof a webpage without navigating away from the webpage. Typically, whenuser 108 is viewing a webpage with browser application 110 and selects alink that links to one or more functionalities provided by remote server104, browser application 110 will be redirected from the current webpageto a new webpage hosted by remote server 104. However, moduleapplication 116 may include instructions such that when user 108 selectsa link displayed in browser application 110, browser application 110will display one or more modules that are displayed within the contextof the current webpage. In some embodiments, the displayed modules mayinclude modules for paying, entering a billing address, a shippingaddress, creating an account, and reviewing and accepting terms andconditions. In some embodiments, the modules may be displayed overlayingthe current webpage. Moreover, module application 116 may includeinstructions enabling browser application 110 to automatically scrollthrough one or more form fields within the modules and between the oneor more modules. In some embodiments, the functionalities provided bymodule application 116 may be enabled by processor-executable code thatmay be executed by one or more processors of remote server 104, providedto client computing device 102 for execution by one or more processorsas part of browser application 110, and/or provided to a third-partyserver hosting the current website.

Remote server 104 may also include a payment application 118 that may becapable of processing payments for users, such as user 108. In someembodiments, payment application 118 may be capable of interfacing withpayment application 112 of client computing device to process paymentson behalf of user 108. Remote server 104 may further include an accountdatabase 120 that includes account information 122 for users having anaccount on remote server 104, such as user 108. Account information 122in account database 120 may also include the locations of merchants,including merchants having merchant-specific content 118. Remote server104 may include other applications 124 providing other functionalities.

Although discussion has been made of applications and applications onclient computing device 102 and remote server 104, the applications mayalso be, in some embodiments, modules. Module, as used herein, may referto a software module that performs a function when executed by one ormore processors or Application Specific Integrated Circuit (ASIC) orother circuit having memory and at least one processor for executinginstructions to perform a function, such as the functions described asbeing performed by the applications.

FIG. 2 is a diagram illustrating computing system 200, which maycorrespond to either of client computing device 102 or remote server104, consistent with some embodiments. Computing system 200 may be amobile device such as a smartphone, a tablet computer, a personalcomputer, laptop computer, netbook, or tablet computer, set-top box,video game console, head-mounted display (HMD) or other wearablecomputing device as would be consistent with client computing device102. Further, computing system 200 may also be a server or one serveramongst a plurality of servers, as would be consistent with remoteserver 104. As shown in FIG. 2, computing system 200 includes a networkinterface component (NIC) 202 configured for communication with anetwork such as network 106 shown in FIG. 1. Consistent with someembodiments, NIC 202 includes a wireless communication component, suchas a wireless broadband component, a wireless satellite component, orvarious other types of wireless communication components including radiofrequency (RF), microwave frequency (MWF), and/or infrared (IR)components configured for communication with network 106. Consistentwith other embodiments, NIC 202 may be configured to interface with acoaxial cable, a fiber optic cable, a digital subscriber line (DSL)modem, a public switched telephone network (PSTN) modem, an Ethernetdevice, and/or various other types of wired and/or wireless networkcommunication devices adapted for communication with network 106.

Consistent with some embodiments, computing system 200 includes a systembus 204 for interconnecting various components within computing system200 and communicating information between the various components. Suchcomponents include a processing component 206, which may be one or moreprocessors, micro-controllers, graphics processing units (GPUs) ordigital signal processors (DSPs), and a memory component 208, which maycorrespond to a random access memory (RAM), an internal memorycomponent, a read-only memory (ROM), or an external or static optical,magnetic, or solid-state memory. Consistent with some embodiments,computing system 200 further includes a display component 210 fordisplaying information to a user 108 of computing system 200. Displaycomponent 210 may be a liquid crystal display (LCD) screen, an organiclight emitting diode (OLED) screen (including active matrix AMOLEDscreens), an LED screen, a plasma display, or a cathode ray tube (CRT)display. Computing system 200 may also include an input component 212,allowing for a user of computing system 200, such as user 108, to inputinformation to computing system 200. Such information could includepayment information such as an amount required to complete atransaction, account information, authentication information such as acredential, or identification information. An input component 212 mayinclude, for example, a keyboard or key pad, whether physical orvirtual. Computing system 200 may further include a navigation controlcomponent 214, configured to allow a user to navigate along displaycomponent 210. Consistent with some embodiments, navigation controlcomponent 214 may be a mouse, a trackball, or other such device.Moreover, if device 200 includes a touch screen, display component 210,input component 212, and navigation control 214 may be a singleintegrated component, such as a capacitive sensor-based touch screen.

Computing system 200 may further include a location component 216 fordetermining a location of computing system 200. In some embodiments,location component 216 may correspond to a GPS transceiver that is incommunication with one or more GPS satellites. In other embodiments,location component 216 may be configured to determine a location ofcomputing system 200 by using an internet protocol (IP) address lookup,or by triangulating a position based on nearby telecommunications towersor wireless access points (WAPs). Location component 216 may be furtherconfigured to store a user-defined location in memory component 208 thatcan be transmitted to a third party for the purpose of identifying alocation of computing system 200. Computing system 200 may also includesensor components 218. Sensor components 218 provide sensorfunctionality, and may correspond to sensors built into client computingdevice 102 or sensor peripherals coupled to client computing device 102.Sensor components 218 may include any sensory device that capturesinformation related to user 108 and/or client computing device 102 thatmay be associated with any actions that user 108 performs using clientcomputing device 102. Sensor components 218 may include camera andimaging components, accelerometers, biometric readers, GPS devices,motion capture devices, and other devices that are capable of providinginformation about client computing device 102 or user 108, or anenvironment therearound. Computing system 200 may also include one ormore wireless transceivers 220 that may each include an antenna that isseparable or integral and is capable of transmitting and receivinginformation according to one or more wireless network protocols, such asWi-Fi™, 3G, 4G, HDSPA, LTE, RF, NFC, IEEE 802.11a, b, g, n, ac, or ad,Bluetooth®, BLE, WiMAX, ZigBee®, etc.

Computing system 200 may perform specific operations by processingcomponent 206 executing one or more sequences of instructions containedmemory component 208. In other embodiments, hard-wired circuitry may beused in place of or in combination with software instructions toimplement the present disclosure. Logic may be encoded in a computerreadable medium, which may refer to any medium that participates inproviding instructions to processing component 206 for execution,including memory component 208. Consistent with some embodiments, thecomputer readable medium is tangible and non-transitory. In variousimplementations, non-volatile media include optical or magnetic disks,volatile media includes dynamic memory, and transmission media includescoaxial cables, copper wire, and fiber optics, including wires thatcomprise system bus 204. According to some embodiments, transmissionmedia may take the form of acoustic or light waves, such as thosegenerated during radio wave and infrared data communications. Somecommon forms of computer readable media include, for example, floppydisk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EPROM,FLASH-EPROM, any other memory chip or cartridge, carrier wave, or anyother medium from which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computing system 200. In various other embodiments of thepresent disclosure, a plurality of computing systems 200 coupled by acommunication link 222 to network 106 (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another. Computing system 200 may transmit and receivemessages, data and one or more data packets, information andinstructions, including one or more programs (i.e., application code)through communication link 222 and network interface component 202 andwireless transceiver 220. Received program code may be executed byprocessing component 206 as received and/or stored in memory component208.

FIG. 3 is a flowchart illustrating a process 300 for automaticallyscrolling through one or more displayed modules, consistent with someembodiments. For the purpose of illustration, FIG. 3 may be describedwith reference to any of FIG. 1 or 2. Process 300 shown in FIG. 3 may beembodied in computer-readable instructions for execution by one or moreprocessors such that the steps of process 300 may be performed by remoteserver 104. In some embodiments, module application 116 of remote server104 may include instructions for performing one or more steps of process300. As shown in FIG. 3, process 300 may be initiated when remote server104 receives a request to display a module (302). In some embodiments,the request to display a module may be received in response to user 108clicking or selecting a link to a webpage or service provided by remoteserver 104 using browser application 110.

In response to the user 108's clicking or selecting a link on a webpageto direct to user to or open up another webpage, the system maydetermine whether the link is directed to a webpage related to aTillable form, an agreement requiring a response, or any webpage thatrequires an input from the user after which the user likely would wantto return to the current webpage. If the link is configured to directthe user to another webpage from which the user likely would want toreturn to the current webpage or if the user likely would want topreserve the current page, the system may display the another webpage inthe module format, by which the contents of the another page aredisplayed as scrollable modules over the current webpage. By displayingthe new webpage as scrollable modules overlaying the current webpage,the user 108 may preserve the current page when the user 108 clicks onor selects the link, without navigating away from the current page.

When the system determines to display the new webpage as scrollablemodules, a determination may be made as to whether there is an activemodule to currently be displayed (304). In some embodiments, an activemodule is a module that has not yet been completed, includes form fieldsthat have not yet been filled in, requires an action by user 108, andthe like. In some embodiments, an active module may be a first orinitial module to be displayed in response to the request. When there isno active module to be displayed, the webpage including the link toremote server 104 may be displayed as active (306).

When there is an active module to be displayed, module application 118may display the active module in context (308). That is, the activemodule may be displayed overlaying or superimposed on the currentwebpage, without navigating away from the current webpage. In someembodiments, the displayed active module may have one or more formfields requiring entry from user 108, and a determination may be made asto whether all form fields have been filled (310). When all form fieldshave not been filled, module application 116 may wait for a command tomove to the next module (312). In some embodiments, a command to move tothe next module may include selecting an arrow, tabbing through the formfields, pressing a Page Down or End key, and the like. When a command tomove to the next module is not received, the active module may continueto be displayed in context (308). When all form fields have been filledor when a command to move to the next module has been received, moduleapplication 116 may determine if there is an error in the module (314).An error may be a form field that has not been filled, a form fieldhaving an entry that is not formatted correctly, and the like. Whenthere is an error, the active module may continue to be displayed incontext (308).

When there is no error, a determination may be made to determine whetherthe active module supports autoscroll (316). In some embodiments, somemodules may be configured to support autoscroll, while other modules maynot permit autoscrolling. When autoscroll is available, the next moduleto be displayed may be autoscrolled to and designated as the activemodule (318) and, as long as there is an active module to be displayed(304), the newly designated active module may be displayed in context(308). In some embodiments, if client computing device 102 is a mobiledevice, the autoscroll to the next module may be adaptive and mayinclude a free and/or natural scroll. When autoscrolling is notavailable for a particular module, a forward navigation arrow may beactivated (320). In some embodiments, each module may include forwardand backward navigation arrows for manually scrolling between thedifferent modules. Typical settings may include disabling the forwardnavigation arrow until user 108 has completed all of the form fields, orhas otherwise activated the next module. Typical settings may alsoinclude having backward navigation arrows always active and havingforward navigation arrows disabled until a backward navigation arrow isselected. A determination may then be made to determine when the forwardnavigation arrow is selected (322). As long as the forward navigationarrow is not selected, the active module may continue to be displayed incontext (308). When the forward navigation arrow is selected, the nextmodule to be displayed may be scrolled to and designated as the activemodule (324) and, as long as there is an active module to be displayed(304), the newly designated active module may be displayed in context(308).

FIGS. 4A-4E illustrate examples of displaying and scrolling betweenmodules, consistent with some embodiments. As shown in FIG. 4A, anactive module, e.g., module 1, may be displayed at a center area in thedisplay. A next, inactive module, e.g., module 2, may be displayed at alower side of the active module and separated from the active module bya predetermined space. When the modules move, the predetermined spacemay be maintained between the modules.

As shown in FIG. 4B, module 2 may be activated and be displayed at thecenter area of the display. In an embodiment, module 2 may be activatedby scrolling module 2 to the center area of the display. Module 1 nowmay be positioned above module 2 and a subsequent module 3 may bepositioned below module 2. The modules may be separated from each otherby the same predetermined space. As also shown in FIGS. 4A and 4B, themodules that a user, such as user 108, may be able to navigate to aremore darkly shaded while modules to which user 108 is not yet able tonavigate to are more lightly shaded. In an embodiment, user 108 may notbe able to navigate to a next module, whether by scrolling or command,until previous modules have been completed.

As shown in FIG. 4C, when user 108 is purchasing an item, a cart modulemay be displayed above the active module 2. When user 108 selects orclicks on the cart, the cart may be opened and viewable above the activemodule. When the cart is opened, other modules may be pushed down asneeded. As shown in FIGS. 4D and 4E, when the active module has beencompleted, the active module may scroll upwards to display the nextmodule, which may then be marked as the active module. In someembodiments, the scrolling may be automatic, or may be initiated by auser command. Moreover, the cart module may remain stationary at the topof the screen above the active module, even as the active module changesas one module scrolls to another module.

FIG. 5 illustrates examples of active and inactive modules andacceptable ways for interacting with these modules on both desktop andmobile. As shown in FIG. 5, an active module is clickable and may acceptthe use of navigation buttons on desktop. While on a mobile device,active modules may be tapable and scrollable but may not includenavigation buttons. In an embodiment, a selectable button may beprovided at a top header area of the display. The button may be labeledwith the name of a module. A user may select the button to open or closethe named module. For example, a button named “CART” may be provided atthe top header area of the display. When the user selects the button“CART”, the “CART” module may be opened or closed. In the desktop mode,the button may be a clickable area which the user may select by clickingon the button. The user also may click directly on the “CART” module toopen or close the module. In the mobile mode, the button may be atapable area which the user may tap with a finger to open or close thebutton. The user also may scroll away from the module to close themodule. For example, in the mobile mode, the user may tap on the “CART”button displayed on the header or on the “CART” module to open or closethe “CART” module. The user also may scroll away from the “CART” moduleto other modules to close the “CART” module.

In an embodiment, when an active module is displayed, a lower portion ofa previous module may be displayed just above the active module and atop portion of a subsequent module may be displayed just below theactive module. In the mobile mode, the lower portion of the previousmodule may be tapable or scrollable to activate the previous module.Similarly, the top portion of the subsequent module may be tapable orscrollable to activate the subsequent module. In the desktop mode,navigation buttons may be provided on a side area of the active moduleto navigate or to activate the other modules. For example, miniatureicons or buttons representing different modules may be provided at theside area of the display. The miniature icon representing the activemodule may be shaded darker than miniature icons representing the othernon-active modules. The user may select or click on the differentminiature icons or buttons to activate the respective modulesrepresented by the miniature icons or to navigate among the differentmodules.

FIG. 6 provides an example of a “Pay with module” with specific rulesand functionalities for this module. The “Pay with module” may beactivated when a user selects a payment link in a website of a merchant.The payment link may be embedded in a checkout page, a shopping page, orany other page that directs the user to making payment over theinternet. In an embodiment, the pay with module may be configured toreceive the user's payment card number, expiration date of the paymentcard, and the card security code (CSC) of the payment card. In anotherembodiment, the pay with module may include buttons for the user tochoose to pay with a bank account or with a payment card account. If theuser selects to pay with a bank account, the module may be configured toreceive the user's bank account number, bank routing number, and theuser's date of birth. The pay with module may require that the use enterall information before going to the next module. In particular, thesystem may check and determine whether the information entered by theuser is in the correct format, such as the correct type or correctnumber of digits or characters.

FIG. 7 provides an example of a “Billing address module” with specificrules and functionalities for this module. After the user enters correctinformation for the pay with module, the system may then allow the userto advance to the billing address module. In an embodiment, the systemmay automatically scroll from the pay with module to the billing addressmodule after the user correctly finished filling in the information atthe pay with module. The billing address module may include form fieldsconfigured to receive the user's first name, last name, street address,city, state, zip code, type of phone number, and phone number. In anembodiment, the user may have auto-complete function in the browser andthe browser may automatically fill in the information into the billingaddress module. If the user has auto-complete but does not haveauto-scroll function on, navigation buttons, such as up and down arrowbuttons, may be provided for the user to navigate to the next module. Inan embodiment, with the auto-complete function, the user may still needto choose the phone type and the phone number to be input into thebilling address module. After all fields are correctly filled in, thesystem may automatically scroll to the next module if the auto-scrollfunction is on.

FIG. 8 provides an example of a “Shipping module” with specific rulesand functionalities for this module. After the user enters correctinformation for the billing address module, the system may then allowthe user to advance to the shipping module. In an embodiment, the systemmay automatically scroll from the billing address module to the shippingmodule after the user finished filling the information at the billingaddress module correctly. The shipping module may include form fieldsconfigured to receive the user's name and shipping address. A check boxmay be provided for the user to select to use the billing addresspreviously entered as the shipping address. The form field for the ZIPcode or letter of city or country may be the last field to be completedin the shipping module. Depending on the country of the shippingaddress, this field may be a city, postcode, or country. If the usertypes in particle word and then uses dropdown menu to complete thefield, the system may auto scroll when the user hits return taps orclick a selection in the dropdown menu. In a case where this last fieldis optional, such as in Ireland, the user may navigate to the nextmodule using navigation buttons, such as up and down arrow buttons.

FIG. 9 provides an example of an “Account creation module” with specificrules and functionalities for this module. The account creation modulemay be activated when a user selects a link in a website or anapplication of a merchant or a service provider for creating a new useraccount. The link may be embedded in a welcome page, a shopping page, orany other page that directs the user to create a new account. Theaccount creation module may include form fields configured to receiveuser's login ID, account ID, email address, password, and confirmationof password. The system may check the email address entered by the userby inline validation to ensure that the email address is valid. Thesystem also may ensure that the password entered in the two fields matcheach other. If all information entered is validated, the system mayallow the user to navigate to the next module. In an embodiment, thesystem may auto-scroll the user to the next module.

FIG. 10 provides an example of a “Terms and conditions module” withspecific rules and functionalities for this module. After the userenters correct information for the account creation module, the systemmay then allow the user to advance to the terms and conditions module.In an embodiment, the system may automatically scroll from the accountcreation module to the terms and conditions module after the userfinished filling the information at the account creation modulecorrectly. The terms and conditions module may provide the user with theterms and conditions associated with the use of the account. A check boxmay be provided for the user to agree to the terms and conditions. Theauto-scroll function may be disabled for the terms and conditionsmodule. As such, the user may be required to manually agree to and hit acontinue button to go to the next module.

FIG. 11 provides an example of autoscrolling and autofilling using the“Pay with module” described in FIG. 6, and the “Shipping module”described in FIG. 8. Moreover, FIG. 11, provides example rules for usingarrow navigation, consistent with some embodiments. In an embodiment,navigation buttons, such as up and down buttons, may be displayed at aside area of the display to allow the user to navigate to and edit priormodules. The navigation buttons may have different colors indicatingwhether the button is operable. For example, a down button may have agray color indicating that the user is not allowed to go to the nextmodule. An up button may have a darker or brighter color indicating thatthe up button is operable to navigate the user to the previous module.

In an embodiment, when the module has the auto-fill function, the formfields may automatically be filled with previously entered informationwhen the user starts typing in one of the form fields. When the formfields are automatically filled, the user may tab or click in the formfields to confirm the auto-fill. The user then may select the navigationbutton, e.g., down button, to go to the next module. In an embodiment,the user may continue typing in the form fields to ignore the auto-fillfunction.

The system may follow the following general rules when implementingauto-scroll of modules. In general, the system may automatic scroll tothe next module after the information input is completed correctly oneach module. At the second module, the navigation buttons, such as upand down buttons, may be provided to allow the user to navigate betweendifferent modules. In particular, the up or back buttons may be activeor operable for most modules, such that users may navigate to previousmodules to edit or make changes to information previous input by theuser. In an embodiment, the auto-scroll function may be disabled orinoperable for certain modules, such as the terms and conditionsagreement module. In this case, the navigation button may be provided toallow users to navigate to the next module.

In modules where the users are required to initiate the move to the nextmodule, navigation buttons may be provided. The users also are allowedto tab through the modules, without errors. The navigations may beconsistently displayed once they appear in the navigation flow. Theusers may be prohibited from navigating to the next module until theinformation input at the current module is completed correctly.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more machine-readable mediums,including non-transitory machine-readable medium. It is alsocontemplated that software identified herein may be implemented usingone or more general purpose or specific purpose computers and/orcomputer systems, networked and/or otherwise. Where applicable, theordering of various steps described herein may be changed, combined intocomposite steps, and/or separated into sub-steps to provide featuresdescribed herein.

Embodiments consistent with this disclosure may provide various moduleswhich may be displayed within the context of the webpage withoutnavigating away from the webpage while providing rules for autoscrollingfrom an active module to a next module. The examples provided above areexemplary only and are not intended to be limiting. One skilled in theart may readily devise other systems consistent with the disclosedembodiments which are intended to be within the scope of thisdisclosure. As such, the application is limited only by the followingclaims.

1. A system comprising: a non-transitory memory storing data on a userdevice; one or more hardware processors coupled to the non-transitorymemory and configured to read instructions to cause the system toperform operations comprising: receiving, via a browser application, anindication that a link has been selected in a first webpage on a displayof the user device, wherein the link is associated with a secondwebpage; causing the browser application to enter a module format inresponse to the selection, wherein the module format is configured tocause a display of contents of the second webpage as one or morescrollable modules over the first webpage; causing the browserapplication to populate one or more fillable forms in the one or morescrollable modules with data stored in the non-transitory memory;determining whether the one or more fillable forms in the one or morescrollable modules are complete; and in response to the determining,causing the browser application to exit the module format.
 2. The systemof claim 1, wherein the one or more scrollable modules is configured tonavigate from a current module of the one or more scrollable modules toa subsequent module of the one or more scrollable modules in the firstwebpage by an automatic scrolling from the current module to thesubsequent module when each fillable form of the current module iscompleted.
 3. The system of claim 2, wherein the user is navigated tothe subsequent module when a down button displayed on the display of theuser device is selected and each fillable form of the current module iscompleted.
 4. The system of claim 2, wherein the user is navigated to apreceding module of the one or more scrollable modules when an up buttondisplayed on the display of the user device is selected.
 5. The systemof claim 1, wherein each fillable form is completed when a number and atype of characters or numbers are filled in each fillable form of eachmodule.
 6. The system of claim 2, wherein a button identifying thecurrent module is displayed at a top header area of the display andwherein the button is selectable for opening or closing the currentmodule.
 7. The system of claim 1, wherein the operations furthercomprise: in response to exiting the module format, discontinuing thedisplay of the contents of the second webpage over the first webpage. 8.A method comprising: receiving, by a browser application executing on aprocessor of a user device, an indication that a link associated with asecond webpage has been selected in a first webpage on a display of theuser device; causing the browser application to enter a module format inresponse to the selection, wherein the module format is configured tocause a display of contents of the second webpage as one or morescrollable modules over the first webpage; causing the browserapplication to populate one or more fillable forms in the one or morescrollable modules with data stored in a memory; determining, by thebrowser application, whether the one or more fillable forms in the oneor more scrollable modules are complete; and in response to thedetermining, causing the browser application to exit the module format.9. The method of claim 8, further comprising: navigating from a currentmodule of the one or more scrollable modules to a subsequent module ofthe one or more scrollable modules in the first webpage when the currentmodule is completed.
 10. The method of claim 8, wherein the one or morefillable forms of the one or more scrollable modules are configured toreceive information related to one or more of a payment account, abilling address, shipping information, account creation information, anda terms and conditions agreement.
 11. The method of claim 9, wherein thecurrent module is displayed at a center area of the display and a topportion of the subsequent module is displayed below the current moduleseparated by a predetermined distance therebetween.
 12. The method ofclaim 9, wherein the subsequent module is not available for interactionuntil the subsequent module has been marked as active.
 13. The method ofclaim 12, wherein, when marked as active, the subsequent module isdisplayed at a center area of the display and the current module isdisplayed above the subsequent module.
 14. The method of claim 9 whereinthe current module is an account creation module configured to receiveaccount creation information from a user and the subsequent module is aterms and conditions module configured to provide terms and conditionsagreement to the user.
 15. The method of claim 14, wherein anauto-scroll function is disabled for the terms and conditions module.16. The method of claim 8, wherein information is automatically filledinto the one or more fillable forms of the one or more scrollablemodules based on previous inputs of the user.
 17. A non-transitorymachine-readable medium comprising a plurality of machine-readableinstructions executable to cause a machine to perform operationscomprising: receiving, by a browser application, an indication that alink has been selected in a first webpage on a display, wherein the linkis associated with a second webpage; causing the browser application toenter a module format in response to the selection, wherein the moduleformat is configured to cause a display of contents of the secondwebpage as one or more scrollable modules over the first webpage;causing the browser application to populate one or more fillable formsin the one or more scrollable modules with data stored in a memory;determining whether the one or more fillable forms in the one or morescrollable modules are complete; and in response to the determining,causing the browser application to exit the module format.
 18. Thenon-transitory machine-readable medium of claim 17, wherein the one ormore scrollable modules include a payment module configured to receivepayment related information from a user and also include a billingaddress module configured to receive billing address information fromthe user.
 19. The non-transitory machine-readable medium of claim 18,wherein the one or more scrollable modules include a shipping modulethat is activated and displayed after fillable forms of the billingaddress module are completed.
 20. The non-transitory machine-readablemedium of claim 17, wherein navigation buttons are provided at a sidearea of the display and configured to receive instructions fornavigating to a preceding module or a subsequent module from a currentmodule.